Feature name
(feature_name)

A feature identifies a suite of applications, an application, a file, or a functionality of the software that needs to be licensed.

It can consist of alpha-numeric characters, without spaces, in the ASCII range of 32-126.

Feature version
(feature_version)

Optionally, the licensed feature can also have a version associated with it.

It can consist of alpha-numeric characters, without spaces, in the ASCII range of 32-126.

Single or multi-feature (key_type)

Specifies the license model as: single feature license or multi-feature license.

Number of features
(num_features)

The number of multiple features in a license. The range for the number of features specified are:

>Minimum allowed = 2

>Maximum allowed = 63

Standalone/Network/Repository (standalone_flag)

Defines the license type depending on then deployment type:

For On-premises and Lease mode:

>Standalone License

>Network License

>Repository License

Long or Short-numeric (code_type)

Determines the license code type. The possible types are:

>Long Licenses

>Short-numeric Licenses

NOTE   Short license codes are now only available for license versions earlier than 8.1.x.

Combining licenses (additive)

Determines how a new license will interact with a license already installed for this feature and version. They can be:

>Additive License

>Exclusive License

>Aggregate License

License output format
(out_lic_type)

Determines the format of the license generated. The possible options are:

>Encrypted License Code

>Concise Readable License Code

>Expanded Readable License Code

Trial or normal license (licType)

Determines whether a license has trial properties associated (trial days and/or hours).

License locking mode (client_server_lock_mode)

Determines the mode chosen for locking a license, including no-locking (unlocked). The options are:

>Client-server locked

>Client-locked

>Server-locked

>Unlocked

Server locking criteria 1 and its information
(server_lock_info1)

The primary locking criteria for server-locked licenses.

Server locking criteria 2 and its information
(server_lock_info2)

The secondary locking criteria for server-locked licenses.

Client locking criteria and information
(nl_client_lock_info)

The locking criteria for a client, for node-locked licensing.

Local-request locking information
(local_request_lockcrit_flags)

The locking information for local request-based licenses, such as repository, grace, and commuter licenses.

Birth hours and minutes

(birth_hours and birth_minutes)

The license start time (in hours and minutes).

NOTE   These fields are relevant for version 16 (and above) licenses. If this field is set, the time and date values are interpreted as per the Coordinated Universal Time (UTC) standard.

Birth day, month, and year

(birth_day, birth_month, and birth_year)

The license start date. If a beginning date is chosen for the license, the application will not run before that date (day, month, and year).

The license end time (in hours and minutes).

NOTE   These fields are relevant for version 16 (and above) licenses. If this field is set, the time and date values are interpreted as per the Coordinated Universal Time (UTC) standard.

Death day, month, and year (death_day, death_month, and death_year)

The license expiration date. If an end date is chosen for a license, the license will become invalid after that date (day, month, and year).

Trial days
(trialDaysCount)

The number of days a trial license can last.

Trial hours (trialHoursCount)

The number of hours a trial license can last.

Sharing criteria
(sharing_crit)

Determines whether license token sharing is allowed for the feature or not. If allowed, then this value is the criteria chosen to share a license. The possible criteria are:

>User name - License sharing on the basis of a common user name.

>Host name - License sharing on the basis of the system where the licensed feature is being run.

>X-display ID - License sharing on the basis of the X-display ID of a UNIX or Linux ARM system.

>Vendor-defined - License sharing on the basis of a custom license sharing mechanism you implemented, which is registered using the VLSsetSharedId or VLSsetTeamId API function. The Unified API-based licensing implementations can set the sharing criteria using the SNTL_ATTR_APPCONTEXT_VENDOR_DEFINED_SHARINGID attribute of the sntl_licensing_app_context_new API.

Hard limit
(num_keys)

Specifies the number of license tokens available for concurrent use. The maximum number of license tokens is the hard limit.

Soft limit
(soft_limit)

Specifies the number of license tokens at which to issue an alert or warning that the maximum number of licenses is approaching. Its value should not exceed the hard limit specified.

Number of instances
(keys_per_node)

Controls the number of copies running on each client node (for client-locked and client/server-locked licenses).

The units or range using which lifetime value needs to be input. For example:

>Multiple of 1 minute(s), maximum 15 minutes

>Multiple of 10 minute(s), maximum 150 minutes

>Multiple of 30 minute(s), maximum 450 minutes

>Multiple of 60 minute(s), maximum 900 minutes

For more details, see Deciding License Token Lifetime.

Lifetime value
(key_lifetime)

The lifetime value.

Holdtime
(holding_crit)

Determines whether license token holding is allowed for the feature or not. For more details, see Deciding License Token Holdtime.

Holdtime unit
(key_hold_units)

The units or range using which holdtime value needs to be input. For example:

>Multiple of 1 minute(s), maximum 15 minutes

>Multiple of 10 minute(s), maximum 150 minutes

>Multiple of 30 minute(s), maximum 450 minutes

>Multiple of 60 minute(s), maximum 900 minutes

Holdtime value
(key_holdtime)

The holdtime value for which the key will be held for a client.

Number of secrets
(num_secrets)

Specifies the total number of secrets for the challenge-response mechanism. The maximum number of secrets that can be specified is seven.

Secrets
(secrets)

The secret strings for the challenge-response mechanism

Private information (vendor_info)

>The additional information that you can include as a part of your license code for identification. You may use it for keeping track of distributors or implementing a variety of licensing schemes.

>Private vendor information will remain encrypted in all license models (whether readable or encrypted).

Public information
(plain_vendor_info)

The additional information that you can include as a part of your license code. It remains encrypted in encrypted licenses and readable in readable licenses, respectively.

License vendor information

(license_vendor_info)

>This field is used for license aggregation by specifying different software vendor info, however, it does not participate in license aggregation. License vendor information is the additional information that you can include as a part of the license code for identification.

>This new field is applicable to version 19 licenses and above.

> License vendor information can be used for tracking distributors or implementing a variety of licensing schemes.

>License vendor information remains encrypted in all types of licenses (readable or encrypted).

Number of redundant License Managers
(num_servers)

Specifies the maximum number of redundant License Managers in a subnet. The number of redundant License Managers can be a minimum of two (when the majority rule is not applied) or three (when the majority is applied) and a maximum of 11.

Majority rule
(majority_rule)

Specifies that majority of redundant License Managers must be running. If the number of redundant License Managers running is less than half of the number of License Managers specified in the license file, then all License Managers will stop servicing all old and new clients.

Commuter license or not (isCommuter)

Specifies whether a commuter license is allowed or not.

Maximum number of days for check-out
(commuter_max_checkout_days)

Specifies the maximum number of days a network license can be checked-out for. The maximum value cannot exceed 1827 days.

Log encryption level
(log_encrypt_level)

Specifies the encryption level of the usage log file (created on the License Manager end for network licenses). You can choose from the following levels:

0 - Set the log encryption level to 0, when you want to allow the system administrator to set the encryption level (while starting the License Manager or through the LSERVOPTS environment variable). Now, if the administrator sets a value between 1-4, it will be applied. However, if the administrator does not set a value, then the encryption level of 2 will be set.

NOTE   If you do not set any level while generating the license, then 1 will be set. Your setting, between 1 to 4, will always override any level specified by the customer.

1 - Allows no encryption. Transaction data will be logged for this license code with no encryption.

2 - No encryption, tags each record with checksum. Transaction data will be readable by the customer, but tampering with or deleting an entry can be detected if the appropriate usage utility (lsusage or vusage) is run on the log file.

3 - Encrypt usage only. Transaction data will be readable by the customer except for license usage data (which will be encrypted), but tampering with or deleting an entry can be detected if the appropriate usage utility (lsusage or vusage) is run on the log file.

4 - Encrypt entire record. All transaction data for the license code will be encrypted. Tampering with or deleting an entry will not be prevented, but can be detected if the appropriate usage utility (lsusage or vusage) is run on the log file.

Few examples of log encryption levels:

>Vendor = Not set, System administrator = 1-4, Conclusion = 1

>Vendor = 0, System administrator = Not set, Conclusion = 2

>Vendor = 0, System administrator = 1-4, Conclusion = 1-4 as set by the administrator

>Vendor = 1-4, System administrator = 1-4, Conclusion = As set by the software vendor

>Vendor = 1-4 System administrator = Not set, Conclusion = As set by the software vendor

Number of subnets and information
(num_subnets and site_lic_info)

Specifies the number of subnets used for site licensing and their details.

Site-licensed applications can be locked to IP subnets. A subnet is specified using a wildcard notation. For instance, the subnet notation, 123.4.56.* refers to the subnet comprising all hosts whose IP addresses share the first three sub-addresses with the specified notation. Up to four wildcards can be used to specify a site, one in any sub-address position. Each notation can specify a group of subnets, for example, 123.*.56.*. Supported for long unlocked and server locked license codes.

NOTE   Site (subnet) licensing is not supported with IPv6 addresses.

Capacity or not
(capacity_flag)

Decides whether the license capacity is allowed or not.

Capacity units and value (capacity_units)

Specifies the units of capacity used to specify the capacity value. The options are:

>0 (Multiple of 1(s), maximum 1022)

>1 (Multiple of 10(s), maximum 10220

>2 (Multiple of 100(s), maximum 102200)

>3 (Multiple of 1000(s), maximum 1022000)

>4 (Multiple of 10000(s), maximum 10220000)

Capacity
(capacity)

Specifies the capacity value as per the units specified in capacity_units.

Grace allowed or not (grace_period_flag)

Defines whether a network license can have grace period enabled or not.

Under network licensing, the grace period allows running a licensed application even when the network is temporarily inaccessible. It provides continuity to use the application under unprepared circumstances such as network downtime or disconnection.

Grace period in days (grace_period_calendar_days)

The grace period in the number of days.

Grace period in hours (grace_period_elapsed_hours)

The grace period in the number of hours.

Clock tamper flag
(clock_tamper_flag)

You can specify whether licenses will be issued or not, if clock tampering is detected on a system.

When the License Manager detects that the clock is tampered, it does not grant a license for that feature. The License Manager will not exit on detection of tampering. Other features will continue to be served by the License Manager.

This check will be applied even if someone sets the clock back after starting the License Manager, and then dynamically adds a license.